docs(substantiate): driver signals — best/ over step counts; G2b unchained-eval rule - #86
Merged
Merged
Conversation
…s; G2b unchained-eval rule
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two driver robustness fixes from live evidence: (1) GKD eval trigger keyed on a best/ checkpoint instead of a step count (this run totals 10,995, not run-006's 11,073 — counts drift, artifacts don't); (2) G2b rule: when the other agents' training completes unchained (best/ exists, no final_eval, no app), the driver runs the read-only evaluate_der for their spec.